
To illustrate our design of a multiple interface we have to implement it into a collaborative environment supporting or even better dedicated to the simulation. This environment should also be extensible enough to be extended with our multiple interface module. We choose to integrate it into the PAMS portal \cite{PAMS:2009}.

Currently, PAMS provides to all the participants a common collaborative interface for the simulation, coupled with collaborative tools like video conference, whiteboard, instant messenger with which they communicate and interact. The common interface of the current version of PAMS includes a parameter panel to initialize and modify parameters of the model, a control panel to run the simulation model, a display panel to observe the evolution of the simulation and a monitor panel to observe variable values.
%%%%%%%%%%%%%%%%%%%%%%METTRE DEUX LIGNES sur la structure interne de PAMS%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%
%PAMS framework is a distributed system based on common components (see Fig.2):
% A web application server based on Jsp, Ajax and Servlet (Tomcat & Sakai) to manage the collaborative web interface that displays models, experiments, simulators and results with a simple, adaptable and didactic structure of data.
% A distributed component based application server (EJB-Jonas) to manage the groupware kernel (execute simulators, manage experiments, inputs, outputs and collaboration).
% A Database (MySQL) to store users, experiments and results.



The generic design highlights that a participatory simulation should have a user interface. 
Integration of the multiple interface into the PAMS platform will not modify deeply the existing interface: we will specialize these panels for each role. Each panel will only keep the elements allowed for a particular role.

After having proposed the meta-model and the DTD of the XML configuration files for the multiple interface, the integration has required two more steps. The first step is to give the possibility to the users to upload their XML configuration files on the server. The third step is to develop an EJB module with an XML parser that can read the configuration file and produce the new interface dedicated to each role. This interface is called specialized interface.


%%
%
%To verify the objectives of above theoretical design, PAMS is used as a most typical. The current version of PAMS is designed by following this construction. To apply this conception to PAMS, beside defining a DTD structure and XML file for a multiple interface, it is important to chose the available technologies that are used to developing PAMS such as JAVA, Enterprise Java Bean, JSP \cite{PAMS:2008}... to program the necessary entities to use this construction. After that, we represent the model GAMAVI as a case study to compare the new improvement with the older.

%\subsection{Integration of the multiple interface for PAMS platform}
%
%We consider that the current version of PAMS suggests a more fully participatory simulation. Currently, PAMS provides a common interface for all participants to simulate with collaborative tools like video conference, white-board, instant message on which they communicate and discuss. The generic design found that a participatory simulation should have a custom interface. This means should specialize the role of each participant whose view and control of the parameters and outputs of the simulation are different. Interface of current PAMS comprises a parameter panel to initialize and modify parameters of a model, a control panel to run the simulation model, a display panel to observe the process of simulation, a monitor panel to view variable values. Integration of the multiple interface for PAMS platform is the same with we specialize these panels for each role. Each panel remains some elements they need.
%	
%To build the interface, at first it should make the design, the definition. After that, they assign different roles of a simulation model to participants as the above generic concept. Each role gives the individual rights of controlling or observing the parameters and outputs.
%	
%Our work focus on three main parts: the first part is to build a general language based on XML structure to define the interface of each individual participant. This file will describe the parameters, the monitors, the displays and the graphs of a model that will be visible and controllable elements. XML is a good strategy to easily combine different modules without problem compatible. The second part is to allow the user to upload the XML file on PAMS. The third part is to build a module EJB with an XML parser to change the old interface for the new with the above specification XML file. This interface is called specialized interface. 
